Dealing with device connectivity issues inside a VM isn't too different from troubleshooting on actual hardware.
Could you show a screenshot of how the Leap Motion Controller enumerates in Device Manager inside the guest OS? That will give us an idea of whether it's the guest OS having a problem enumerating the device, more so than the "Leap manager".
If you don't see the Leap Motion controller under Imaging Devices or any other node, then the problem is higher up such as with VirtualBox or the guest OS. Whereas if you see problems like a red x or a yellow question mark, we can troubleshoot those issues with approaches like the WinUSB driver (C:\Program Files (x86)\Leap Motion\Drivers\dpinst64.exe).