Yeah, my bad. Thanks for pointing that out Zoolook. I should have said "core-for-core", since my reference was to a single core in each case.
However, this raises the troubling notion that a dual core machine is somehow faster than a single core machine. I have always had trouble with such references that companies make (Apple too) about a dual core machine being "twice as fast" as a single core machine. In general, this just isn't true. Such a machine may feel more responsive because it can do more things at the same time, but in general, when one looks at any one thing it is doing, that thing isn't any faster just because there are more cores.
It requires excellent software design to extract maximum benefit from multiple cores. All too often on a multi core machine you will see a highly CPU intensive, but single threaded, program either occupy one core to 100% while the other one loafs, or swap back and forth between the two cores. The net result is an overall load of about 50% on the machine. More importantly, subjectively the job being performed doesn't get done any faster. In fact, with dual core swapping, it may even get done a little slower. This is a case where more raw GHz per core would be more effective than more summative GHz overall.
This observation continues to motivate my desire for faster and faster single cores. The fact that you can now get lots of them in a single package is good, but I want each one to be faster. Try doing any heavy handed work in Photoshop and you will immediately understand why this is of value!!