Originally Posted by kiwidude
Not something we can change for 0.6, it is a non-trivial piece of work. Will add it to the list for future consideration though.
Care to qualify this with an example from the 0.5.907 beta in particular of where this still goes wrong? I agree there has historically been issues, but I fixed a whole bunch of them (and in doing so added a new problem in 0.5.906 which was fixed again for 0.5.907).
No case in 907, that I have seen (Your fix may be why I have not seen any
The thing I have run into, have already been identified (and a fix committed