All of the sudden I am getting a leaked object ' SharedCursorHandle' when exiting. The same code has worked for over a year. (On Windows)

The only happens when I set a components cursor to a cursor created from an image, an Alert appears that changes the cursor to the NormalCursor, and then the component is deleted still containing the cursor created with an image. I think this is the combination

 How is this possible? Any ideas?

Can't really think how that could happen unless you're leaking something that contains a MouseCursor.. Got any static objects that might hold one? If you have a file static then the order of destruction might have changed, making this trigger a false alarm if it gets deleted after the leak-checker's internal static object.