HASP Protection

Hello,
i am not well versed in anti-debugging techniques and i have an application i am trying to get working that is protected by a usb hasp key. i have a license and a key, but no matter what i do the damn thing detects a debugger even when they are not running. i have no issue with requiring the hardware key, but the anti-debugger checks are annoying to the point it has recently BSOD the computer while i was working. Of course the company won't remove the protection, their solution being to run the application on a secondary machine accessing things remotely, which i am doing for the moment. But the damn thing is a library i am programming with so testing everything remotely is just a pain at times. i have been looking into the application in hopes of finding the main entry point past the anti debugger checks, but this thing seems to use every anti-debugging trick i have been able to search for on the internet, and also inspects the starting bytes of imported functions to check for 0xCC and other common patches. So far i have not been able to get it to not detect that visual studio is present, much less the more advanced ida.

Almost all functions are manually accessed through GetModuleHandle and GetProcAddress calls.

IsDebuggerPresent
NtQuerySystemInformation
CloseHandle
GlobalFree
CreateToolHelp32Snapshot
...And i don't know how many other methods are being used. i am just trying to find information on getting around these. It doesn't help that the program code is swizzled all to hell with "self-modifying" jumps, etc, so i can't even determine which anti debugging technique is actually being successful.

Do you know of anything that might help me in this area? Or am i just doomed to have their tech support on speed dial (not that that helps since they are in an entirely different time-zone!!...arg!)?

Thanks in advance.