I just installed v1.3(1) again in order to check.
It does in fact not work: cpvnm memory usage does NOT raise over time, but cpu load is quite high (3-4%) with nothing going on. In the CP Manager on the VM host, everything looks ok, there are MIDI settings, CP to MIDI, MIDI to CP correctly displayed for all machines, even the VM Win machine. However, in the CP Manager in the Win VM, devices are created and destroyed all over the place. At least the CPVNM did not crash.
I installed 1.3(2) again. On the VM Host side, everything is correctly displayed in the CP Manager. CPVNM cpu usage in the Win VM is quite high (5-7%), memory usage raises. The CP Manager does not show the the devices correctly. It seems as if the Midi settings, CP to MIDI, MIDI to CP devices are linked to the wrong root devices. The "SM-1" (desktop PC) root for example does NOT show any sub devices, whereas the MBP-1-WIN (Win VM) devices shows multiple "midi settings", "cp to MIDI" "MIDI to CP"... selecting different root devices alters the sub devices - they get more and more and completely messed up regarding their order...
It's a pity, because I am developing a "audio over copperlan" solution, hosting ASIO devices on the Win side and/or CoreAudio devices on the Mac side, with the "side effect" of reducing latency for audio back and forth between VM Host and VM guest as the net is much faster as emulating a sound card...