Yes, I should have stated that Spybot sometimes has issues with Firefox cookies on some systems, not all. I don't think we've ever found a specific reason, though I personally suspect either different Firefox versions or configuration are involved.
This is why I don't think it's worth messing with cookies with Spybot. It simply absorbs Patrick's time in development to keep up with changes in the internal cookie handling of each browser. Since the browsers generally manage cookies well enough themselves at this point, this is an utter waste of resources. Scanning and deleting cookies after the fact or 'managing' them is even more worthless as protection, since they've already performed their function between scans.
The rest of Immunize is static protection in that you must constantly update and re-immunize to keep current. This model is outdated compared to the newer dynamic protection provided by real-time agents similar to TeaTimer. And ActiveX blocking is already performed by Windows Updates for certain modules, a few of which Spybot overlaps. With the improved ActiveX handling in IE7, I don't see a need to fill my registry with hundreds of ActiveX 'KillBits' or 'Restricted Sites' 99% of which I'll never encounter anyway.
Obviously, Immunize isn't replaced by IE7 alone, but combined with a current Antivirus/Firewall/Antispyware with real-time protection for known ActiveX and other malware, it's not really necessary.
Wasn't happy to loose the hard drive, but it forced a 'spring cleaning' as a side effect, which is good since it hadn't been rebuilt since late 2004. It also avoids the issue of performing an Immunize 'Undo' which would have removed any ActiveX KillBits that overlap with past Windows Updates.
