Let me know if you have a better solution for this. The issue is that, when run synchronously, _spotLastControl spots the previous control momentarily (and visually appears spotted ever now and then) before _spotNearestToPointer spots the correct control. The logic for this fix is that _spotLastControl will run late enough where the last control will not be visually spotted; either the last control gets spotted right before the nearest control is spotted without any visual discrepancy, or the nearest control is spotted first and then _spotLastControl is run, but ends up spotting our nearest control as oLastControl has already been updated.