The following behavior only happens under Windows XP, not under Vista, btw.
Moving any explorer window under or around an ObjectDock zoomer (no matter what the settings) works great and at full speed. HOWEVER, if any window is under a zoomer when I run the mouse over the zoomer (hence activating it and/or bringing it to the top), dragging future windows will cause the window drag to strobe at 1/10th the previous refresh as the CPU goes to 100% (3 ghz P4). As if something is fighting with something else for "priority".
This happens with Winamp windows, etc. etc. Anything that is behind the dock when it pops back into the foreground triggers this behavior. To reset thing, I just need to quit and restart object dock. The zoomers will then return and explorer window dragging behaviour will be normal again UNTIL I activate a zoomer if it's in front of something, and then SLOWDOWN again.
TESTING/SYSTEM NOTES:
With Winamp, it doesn't matter which skin, modern or classic.
I ran Rocketdock as a control and it doesn't display this behaviour under any conditions or circumstances, but of course it only runs one dock and i use 5. But perhaps something about the way it layers or draws is distinctly different from ObjectDock and I offer this info in the hopes that it will help you narrow down what's happening. 
I've noticed this behavior for at least six months perhaps as much as a year and a half and I only finally managed to figure out the combination of events that duplicate it reliably. This is also a test machine, so if this had been on my primary production machine, it would have driven me crazy long before now. 
Fortunately, Windowblinds appears no cause difference, running or unloaded. But if something remains wedged in the OS even when "unloaded" that might mean there might still be a connection. Let me know if I should do an uninstall of Windowblinds to test this.
Tabbed docks don't seem to cause the same problem or at least not to the same degree.
This is a 3 ghz P4, 1 gb Ram, Quadro FX 2000 w/128mb display card, latest Nvidia drivers 163.xx series, under Windows XP SP2 (fully patched).
As importantly, I just test installed this on an AMD laptop with XP and ATI on board graphics using Windows XP as well and the results are identical. So it's not an ATI vs. Nvidia or AMD vs. Intel issue.
Let me know if there is anything else I can do to track this down. 