Fix dispose pattern for releasing the RCW object.

Use `ReleaseComObject()` instead of `FinalReleaseComObject` to avoid creating stale references to the RCW of a potential singleton COM object.

Author: lauxjpn

src/System.Data.Jet/ComObject.cs

@@ -10,15 +10,12 @@ internal class ComObject : DynamicObject, IDisposable
     {
         private object _instance;
 #if DEBUG
-        private readonly Guid _trackingId;
+        private readonly Guid _trackingId = Guid.NewGuid();
 #endif
 
         public ComObject(object instance)
         {
             _instance = instance;
-#if DEBUG
-            _trackingId = Guid.NewGuid();
-#endif
         }
 
         public ComObject(string progid)
@@ -111,24 +108,17 @@ private static object WrapIfRequired(object obj)
             return obj;
         }
 
-        private void ReleaseUnmanagedResources()
+        public void Dispose()
         {
+            // The RCW is a .NET object and cannot be released from the finalizer anymore,
+            // because it might not exist anymore.
             if (_instance != null)
             {
-                Marshal.FinalReleaseComObject(_instance);
+                Marshal.ReleaseComObject(_instance);
                 _instance = null;
             }
-        }
 
-        public void Dispose()
-        {
-            ReleaseUnmanagedResources();
             GC.SuppressFinalize(this);
         }
-
-        ~ComObject()
-        {
-            ReleaseUnmanagedResources();
-        }
     }
 }