> just to push this thread a bit: what is the prefered way for dealing with this
> issue? any idea when this will be solved in an official release?

With exactly what issue? With getting this in official release - sure it
is in the next release.

Roman