Hopefully we will see the fix in the next dot-release
I'd just like to caution ones expectations and even though Darius said "We now have a fix prepared for this issue internally" nonetheless he also said "although I can't say when it will make its way into a public release of VMware Fusion" and if past experience tells me anything then it's not likely to make it into the next "dot-release". That said, it will eventually get there and we'll just have to wait and see when. 