Well, I guess you're right, and I agree. I inherited the code and yes, it won't stay this way.

But my question is rather why does something like this occur - it did work for 2 years and it's perfectly valid T-SQL, so why does SQL Server suddenly decide it has to go into a spin turn-around?

It was consistent and reproducable, I tried it with various cursor filters, about 20 times.