Reverse engineering to get a definitive answer as to the actual code for a complicated application is unlikely, since there are many ways to achieve the same output from loops or choice structures. It is easier to get a statistical list of possible treatments of the inputs by testing several of them. You are likely to get more detail from looking at the assembly code outputs from EDB-Debugger, or OllyDbg. As you probably noticed, the assembly code for Linux and for Windows applications are basically identical. High-level languages like C and C++ are just ways to get at the assembly code that can be easily converted to machine code to tell the machine what to do.

Stresstesting your Windows hosts comes down to checking their ability to take many inputs over a short period of time, on any open ports whatsoever. Remember, when stress testing, that you will make a lot of noise on the network, and any intrusion detection tool configured properly will notice your attack. You may also knock the target machine off the network, so you had better alert the management before you start your test.