I updated the benchmarks now, pixel rounding is now off (although i didn't get very much improvement after re-running the tests).
SgtConti If i'm not mistaken, then the framerate of C2 is locked to 60fps (or perhaps that's just the refresh rate of your monitor?) and while it should be the same in CC, i had to figure out a way of manually calculating the current fps, which probably isn't too precise (the project has it set at a fixed rate of 60)...
As for the time testing takes, it is so because new sprites are created every 5 ticks, as opposed to every single tick. If you want it to be faster, you should download the .cap(x) files and edit it to say "every tick", i can update the .cap(x) files for you, if you want this (although giving you pre-made .exe files will take a couple of minutes, as my upload speeds are not the best).
Update: I made a version, which should work 5 times faster and thus be more useful for modern computers. Just get the "every tick" version...
Aphrodite I used the latest version of CC (r2) and a somewhat recent one of C2 (r15X), i'll check and update the main post. Also, it's a bit too early to speak of playable games that can be used to compare the performance, as there still are a couple of problems that need to be solved, for example, the speed at which the applications run (what SgtConti had) and the optimal parameters for both CC and C2, so everything is fair...