Thanks for your feedback and for voicing your concern regarding iLok.
First and foremost, our main reason for moving to iLok was to allow us concentrate on product development rather than copy protection.
You see, our own authorization system is not perfect, and many users asked for offline authorization functionality and the ability to easily carry their licenses on a mobile device as they move between different studios.
Maintaining and supporting this functionality in our own authorization system would take quite a toll on development resources, QA and web integration. Therefore, it was a logical choice to integrate the copy protection by PACE, the most experienced leader in their field and the most widely used, to provide the functionality and support our users have requested.
Furthermore, the amount of CPU resources a plug-in takes is completely up to the developer rather than PACE, and if implemented properly, the additional CPU resources required for iLok are zero.
A USB iLok is NOT required for authorization, and we still provide 3 authorizations with every license. Also, you now can have it on an iLok just in case you're working in another studio or as a backup.
Hope this clears the water.