Rather than 1 process, it seems that FETCH_APICursor is recorded thousands of times so the cumulative effect is total CPU.
In SQL profiler, this shows as cursor fetch etc. but for all users.
The application uses cursors heavily (don't ask).
Is there anything to check as to why there would be more calls to a cursor than before, such as tempdb issue?
There is nothing in SQL logs.