So hang on. You want to test the graphics, cos I've already told you that's slower, but you don't want to test the disk cos you know that's much faster? Talk about rigging the results! I think a fair comparison tests all the parts. For me, compiling a lot of C, the disk access is an important thing and makes using an emulator worthwhile. The actual act of compilation is slower. The overall result is that time is reduced. If you don't think the I/O system is a key part of what makes for a good platform then I think you should probably stop making your statements about system performance
Truly useful tests are what you do day to day. Reflow a document in Impression. Render a complex webpage in Oregano. Compile some source. Unzip some archives. Play a game. Watch a 'demo' (eg !K2). Doesn't that sound reasonable?