sql 2005 doesn't appear to be quite so good at deciding if it should recompile a plan, although I've no direct tests to prove this only seeing what happened to Navision.
Microsoft issued service packs to remove the fast statements from the Navision application becuase it did so much harm - we had over 500 plan guides forcing recompiles whilst we waited for the sp patch. Of course the constant recompiles caused other problems ( oh joy! ) if nothing else this should indicate the risk of using FAST - not every change or additional feature to sql server is always for the best, and quite often there's a "dark side" to such chnages, such as for FAST , varchar(max) and such.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/