As I said I did two years ago, the FreeBSD handbook shows, and others have said, we have no issues with this.
Phishfry brings up an interesting question.
I beg to differ here. Actually, there are a bunch of uses where more abstract support from 3rd-party tools might be nifty. For instance, think installation libraries, multi-image install sticks and the like, used in large, living professional environments.
FreeBSD's installation process has - certainly in the past - had issues with compatibility. For instance, booting/installing with HP iLo always was a mess, success depending on iLo type, iLo firmware version, installation file type (more recent ilos support both memstick and ISO), and even file access type (iLo supports mount-from-client image or drive and mount-from-webserver). More recent ilos work with bringing the ISO in as a virtual USB device, and I've seen my share of installations hanging not finding that, being too fast or too slow for it to appear, and even completely balking at the device, even though FreeBSD in General always supported it.
Having one tool that reliably sorts out this crap and can match whatever the situation demands would have been helpful in many cases. But as things are, HP - like most other vendors - hide behind the it's too complicated anyway excuse.
So, no software ecology is so perfect that it would not, in any case, benefit from support by third party tools. "We don't need that, anyway" seems too easy an excuse to me.