Sig:
I may have placed my words wrongly, but basically my idea was that VB executables are larger than its ASM counterpart. Upon experience, I can make a small window with buttons, text boxes, and winsock routines, in Win32 ASM (host-ip resolver proggy) and upon compilation it only takes around 8K in size. In VB it takes a whole lot more, and to me it is garbage. And if you check the binary with a hex editor, you will see some things that are oddly placed in it. Run a disassembler on that executable, and it will take you a while in trying to figure out what it does, if ever you succeed in doing so.
I have seen some VB decompiler (freeware/shareware) that claims that it can convert your executable to VB source code, but only if it was created using VB4. I don't know if it is real or not, since I haven't bothered using it.