Hi,
in the meantime at least one similar error was fixed and is available in the last public release. I would assume that the described error not occur anymore. If I'm wrong, I'm happy to help investigating in this issue(having some code snippets would make it easier for me).
Alex