You may not use other applications. The rest of us might.
So what do you use that looks inside the new corel file structure and how does it save you time?
Not everyone has disk space to throw around.
I'm not asking for mandatory no-compression - just an option that we used to have and that is now gone. X3 had a checkbox that would allow you to either compress or not compress raster data. I would leave it off while working with files actively and then turn it on for a final save (as well as embedding fonts) for a final archival version. X4 still has the checkbox, but it does nothing as the save routine always packs the contents into a compressed zip as the final step. If you like this, great. For all vector files I find it fine. But it would have been much better if they provided an option for a package that didn't have to compress and compress again and compress again for those who don't want to wait and have plenty of disk space. When working on collages, layouts with embedded bitmaps, etc. the new save routine is definitely slower for me, in minutes, than the old option. And it seems an area that could easily be better with little programming effort on the developers part.
X4 is routinely using all 4 cores of my Quad.
I would pay good money to have it utilize the multiple cores of my quadcore E5472 running 32-bit vista. Here is what I get while saving with X4 while I wait:

The OS rotates the thread among cores, but the utilization never hits close to 100% or even 50% of the 4 cores.
So most of the computer's processing power is idle, unused, while corel does it's new mandatory slow zip routine and I wait for it to save whlie X3 saved in seconds with the compression option off. Granted it's not a huge amount of time, but I figure each project I save around 90 to 110 times. Multiply that by a couple minutes extra lost time each time and you have a loss of productivity from the new version.
It would be the best of all worlds if corel could make X4 fully utilize all the available cpu cores to do the new mandatory zip routine. I don't mind tossing in another CPU to give it 8 cores and would then have no complaints. But with a routine that is only using 1/4 of my available resources and 1/8 of the resources I would gladly provide for it, while I wait, while before it was nearly instant, is less than ideal in my book. It could be much better.
If it can't be multithreaded, why is the compression of the zip necessary for the new structure? Can't the new struture easily exist just fine in an uncompressed or super-fast low compressed format, optionally, to provide options so everyone can have the best of all options?