Reduce size of compiled binary

Hey /prog/, I'm making a remote control tool that works over Tor  because reasons.
But Tor itself weights 3Mio and my final executable is over 1Mio upx'd.
I'm compiling in plain C with Visual'12, have activated all the size optimisation but it's not enough. The client must be able to transfer itself over the network very fast and fit even on small embeded systems.

So do you know of any methods to reduce size further, or any packer better than UPX ? I don't care if it makes my code really slow, but size is critical.

>>15
>output the C code to be able to decipher some of the OPcode
And why would I want to do this ?
Trying to maintain 3Mo of compiler-generated, uncommented, assembly would be batshit crazy.
As I said I'm going to modify the tor implementation, but I'll make it in plain C.

I'm going to look into porting to smaller libs later. First thing is removing the useless functionnalities like bridge/relay, hidden service and the fuckton of runtime options I don't need.

>IDE? Why do you need one?
Well there's a reason why people use them. Having stuff like autocompletion, IntelliSense,"Jump to definition/declaration", or just the formating of compiler output saves a lot of time.
I'll try Geany, if not I'll probably try C::B again.

>And then make a repository for other to take a look. I am interested in the project, as you can tell.
Well, it's a remote control tool, (probably) no one's going to decompile it and study the assembly. But giving the source code is just calling for someone to exploit it. I might want to trust security by obscurity this time.