Problem is actually similar in both engines - in some cases, we changed
'natural' quad splitting order to alternative one, without properkly 'notifying'
UV/VCol/other tessface data about it.
So code would use a 'wrong' triangle of UVs etc.
Solution for BI is rather simple and hopefully does not break anything.
Solution for Cycles is not so elegant imho, but coul not imagine a better way to do it...