Thanks! That fixed the problem.
I removed the automatically added exclusion, and manually added it back in for the entire folder containing the executable. I also added the executable to the Protocol Filtering > Excluded Applications as Arakasi suggested.
Thanks for being helpful and responsive.
Marcos, you might want to check if automatically added exclusions are bugged, and file a formal bug report if you can replicate my problem.