There are a few ways to bypass HRADBA's memory scanning (eg. kicks for #138); directly patch the memory scanning detection algorithm it uses to aways say 'Status: OK'... or implement some kind of memory hiding element in your own custom built trainer (it's called 'rootkit' technology- read about it briefly
here).
HRADBA.dll is loaded into vietcong.exe's address space; and can (try) to read any of the processes memory directly; making it hard to beat using most well known API hooking techniques. This is because HRADBA doesn't use Windows API functions like ReadProcessMemory() to scan memory, like PB (last time I checked) etc.
I'm currently implementing a user-mode version of a very new memory hiding method called Shadow Walking- which can be read about
here. When done correctly- all trainers, new and old will not be detected.
I hate to say it- but you really won't get anywhere unless you know
some programming.
Subsky