Well I wouldn't call them false positives when you set loose a signature based scan, it will find them if you have it scam memory in the custom scan that you used.
These are locations in memory, related to adaware having placed unencrypted virus signatures in memory, so there is no file to actually perform any action on. It isn't saying aawservice.exe is infected but that is the process responsible for placing them in memory.
Personally I wouldn't give AdAware hard disk space as it is a much depreciated application now and for me committing a sin in placing unencrypted virus signatures in memory where another security application looking for virus signatures would find them.