Yes, armadillo's CopyMem protection creates a new process under a debugger (the first process), so the only real good way to patch the process is either program your own custom loader which can patch the second process when it gets created, or unpack the protected app (which you've tried to do already).

Out of curiosity, did DilloDumper do anything at all on this target ? I'm thinking it must have dumped it at least for you to be able to disasm it...

I'll have a look at it tomorrow at work

-Lunar (Working on some new Arma toolz)