Workaround to fix #448 and maybe #428

RemoteTechArchive.cs - Modified CheckRange to return true if the vessel
is currently in the prelaunch condition.  This prevents the archive from
showing as out of comm range during initial start up when RemoteTech
seems to have issues returning the correct value reliably. ( #448 and #428 )
BindingManager.cs - Added a null check before disposing the
flightControl variable.  I have had issues on and off with this throwing
null reference errors when reverting or going to the space center.
Removed check for the current volume being in range and replaced it with a check for the PRELAUNCH situation.  Because we changed the range check to return true in this situation, this one check is enough.