It does not always run at 100%.
I'm running the demo on my Athlon64 3GHz with 1GB RAM, 6600GT graphic, detonator 91.31 under W2k and it does only uses 90% CPU on average, rendering 75 fps in 1152x864x32 .
ButI think there's a missunderstanding: That windows reports 100% CPU in task manager does not mean the CPU is really working hard all the time.
Look at the se5 interface - it runs basically in front of everything, in fullscreen, as most games do. To do that, it creates its own "drawing surface" and does not rely on the explorer to generate its windows/menues.
Same with the event loop: to maximize responsiveness, it uses its own complete with its own 'idling' .. . If the actual workload from player input or AI calculations is low, first the FPS go up as the game can render more frames - up to some limit set by the programmer. After that, the program uses its own idling routines, therefore the win taskmanager can never realise that the CPU is in fact doing nothing.