Not to fan the flames here, but the CIM module takes the card details, passes them to a secure storage area AT AUTHORIZE.NET and that is it. What that means is that you can repeatedly charge their card without storing their card on your server. With standard modules, like the authorize.net module, the card details are stored ON YOUR SERVER, and you charge their card based on the data stored ON YOUR SERVER. With the CIM module, you charge a card number that is stored in a secure area at authorize.net, thereby reducing your risk of accidentally exposing the number.
So, like Matt said, it does not completely solve your PCI compliance issues, but by you not storing the card details on your server, it greatly reduces your risk.
You need to relax and act a little bit more professional in this public forum. You're giving a very poor image for your business. Had you read the sales page for CIM at http://www.authorize.net/solutions/merchantsolutions/merchantservices/cim/ before blowing up, perhaps you wouldn't look so foolish.