Yeah right, because every student knows that it's the matlab calculations which makes the labs take so long time, not to read the exercise, understand it, figure out what to do, solve it, write down whatever you need to do, draw conclusions from the answers, write a report..
Labs? I'm talking about REAL Matlabbing, where you write a few function files, an overall script, and you plug in a bunch of different combinations and make the program run each time. Trust me. Last year, I was using a Matlab script to calculate funky stuff in optical fibres. I'm serious when I say some of the simulations took over a day to run. And that was 1st year!!!
So when someone like me is trying to run a program I, or someone else, wrote to optimise an aircraft design by doing a calculation, changing the parameters and then rerunning the program, over and over, you don't think that's going to take a lot of time, and a few hours cut off the end by using a slightly faster processor would help?
Or, in Solidworks, last year I made a model that completely ate the Uni computers. They really couldn't handle it, taking minutes to render each frame, and calculate all the collision detections. I believe the Uni computers had integrated graphics, which may not have helped much with the rendering, but when the computer decides to give up, and just display everything as rectangular coloured boxes, I'm pretty sure a dedicated graphics card and faster processor would help.
So, yeah. I completely disagree with your implication that Matlab, or other professional applications, will not eat too much from your time if you don't spend a little more on a faster computer. And I reckon a 2.2 or 2.4 SR MBP would be quite a bit faster than any computers you are likely to find in a Uni lab. I know I don't have easy access to anything close to a 2.4GHz Core 2 Duo and 8600M GT.