I would prefer to devote that time to completing the 64bit implementation rather than adding to the native implementation. I’m unsure if 64bit will resolve the issue or if it will just push it off until the driver consumes even more memory. The real fix can only be implemented in the ASCOM driver which is what is leaking. But 64bit may provide enough headroom for it to go on for a while.
So the next question is “So when will 64bit be complete?” unfortunately I don’t have a great answer here but we should be able to start pushing out something within the next couple of weeks to adventurous testers.
Jared