By using a yielding timer event, a long-running event could be interrupted by another event, which resulted in events being processed out-of-order and events being processed non-atomically. This, in turn, caused a difficult-to-understand test failure.
By making the automation timer events non-yielding, the UI automation tests are more likely to be reliable.