I've put Verve Metaboxes to work on a couple client sites and find it very effective. But I find myself commenting out the post_type_supports() requirement for 'custom-fields' in verve-meta-boxes/admin/meta_boxes.php
Removing custom-fields from supported post features has the effect of removing the default "Custom Fields" edit UI - which is exactly what I want. After defining a user-friendly custom UI for postmeta storage, I don't want the "Custom Fields" metabox also hanging around. But due to Verve's post_type_supports() requirement, it does unless I also configure Adminimize to hide "Custom Fields".
It looks to me like (with the exception of revisions usage) the WP core is using post_type_supports() to control UI elements, not to circumvent data storage or retrieval. If you still decide to stick with post_type_supports() requirement, please consider at least providing the option to hide the "Custom Fields" metabox.