Comment 1 for bug 1083094

Cannot reproduce this. Likely because I have a SSD HD and everything is too fast for me.

There is little chance to fix this either way. Vim calls CursorMoved whenever it feels like it, but we need to rely on it being called *often*. Your bug likely describes a situation where it is not often enough and ultisnips gets confused about cursor movement and editing commands you might have made.