We already monitor reorgs and there are now hard limits (not that they are needed yet, but in the future with unknown trust nodes it may) in SolidCoin so I'm not sure what you're getting at here. Any transactions from a wallet that lost transactions in a reorg would readd them. You need to check the code again.
I think the wallet will
probably re-add the transactions if they don't conflict with anything in the post-reorg chain. Also, there's a rather big security related reason that Bitcoin doesn't have hard limits on reorgs.
Not deleting 0 conf transactions from a wallet is a bug in bitcoins handling of reorgs, SolidCoin fixes that bug.
It's not exactly a bug. The Bitcoin developers are opposed to making transactions disappear like that because they're useful for diagnosing double spends after the fact.
God.. soneone so connected to Solidcoin and its various "strange" surroundings (The "dick" that obviously mined a large chunk of the early coins.. the dissapearance of the "dick" and the ddos on BTC pools at the same time...) shouldnt accuse anyone of anything.
Fun thought: anyone that managed to figure out the vulnerability in signing the even blocks early enough could probably have used it to mine a disproportionate percentage of the early coins by exploting it to rewrite history into a version where they mined all the coins.