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.
Check to see if we are using a RemoteTechVolumeManager, if so check the range for the current volume without throwing an exception.