1964 has the same problem as well.
Both my cores are active, affinity set to both cores, and it is giving me bogus readings, such as idle 300%+ and negative values. My system is in great shape and up-to-date (Windows Update, DirectX June 2006, chipset drivers, latest BIOS, the works).
Setting to one core fixes it, but of course the limitation in the emulator is still there.