But, folks really ought not be encouraging this sort of thing, in general. Unless you really know you need some specific version of software, and why, you should probably be using the OS-provided packages, which are better tested (so they're generally more reliable), better supported (so you can complain to someone when you run into a problem), and more widely used (so you can find people talking about your specific version when you hit up Google for advice).
Anyway, I agree. /opt is the socially acceptable place to put random crap on a system.
/usr/local/ executables, libraries, etc. not included by the basic operating system
'/opt' is not documented by hier(7) on FreeBSD, Mac OS X, or OpenBSD.
The only way I feel comfortable compiling software into my system because I KNOW I can delete it by just removing the directory created inside /opt.
The only tricky part is making sure your compiled binaries in /opt/*/bin are in your executable path.
/usr for stuff installed by apt-get.
/usr/local for stuff I install with "./configure && make && make install" or similar commands.
/opt for self-contained application bundles.
Wikipedia (http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) says it's for "Tertiary hierarchy for local data, specific to this host."
Yes, that is called "/opt", not /usr/local. /usr/local is for local extensions to the operating system itself, not applications.