Heh, yeah, school is great in that respect.
I got my hands on Adobe's Production Studio Premium for a whopping $200. That includes Adobe After Effects 7.0 Professional, Adobe Premiere Pro 2.0, Adobe Photoshop CS2, Adobe Audition 2.0, Adobe Encore DVD 2.0, and Adobe Illustrator CS2. It's a pretty sweet deal considering that this would cost $1700 otherwise!
Personally, I have to disagree with Bugzilla. This isn't a rant against macs - I'm 99% sure I'll be getting a Mac Pro for my next purchase. And hey, what programmer doesn't like Unix (I'm a CS student)? I could rant about Windows Vista right now but I'll refrain.
Versions of Premiere that predate the 'Pro' nomenclature really did suck in many ways. Premiere Pro 1.0 was a big advancement and was an entire re-write of the code base. As such it was certainly buggy at times. This didn't surprise me much since it was a 1.0 release. Premiere Pro 1.5 was a big improvement stability wise and really didn't have any problems. With Premiere Pro 2.0 stability problems are completely a thing of the past (assuming you have a stable system to begin with...) as far as I can tell.
I'm quite torn actually. Since I'm probably going to be moving to Macintosh I'm debating whether to continue using Premiere or move to Final Cut (Adobe recently announced that their entire production studio will once again be available on mac which was facilitated by Apple's move to intel chips). As it stands *right now* I feel Adobe holds the crown for being a fully integrated suite with ease of use. I do suspect that this will change when Apple releases the next version of it's studio package though.
With the new Premiere code I think many Mac owners will be a bit surprised when they get to play with it again. It even has some features that FCP doesn't currently have - curves (that one shocked me), 32bit color correction and a few other things which I'm sure Apple will soon remedy (especially with the acquisition of Silicon Color).
In the end I will probably move to FCP myself for its integration with compositing apps like Shake (and whatever comes next) since I like the node based paradigm more than After Effects for this type of work. Still it's a hard decision and I might just write some Python code to link various parts of the Adobe suite with Apple's. Get the best of both worlds.

In fact, I'm pretty sure I'll be doing that!