On the subject of index maintenance...
I went for 2.5 years with virtually no index maintenance on my production box. With that I can tell you that it IS more important to keep statistics up to date that to keep fragmentation low BUT... you cannot simply ignore fragmentation.
Now, that being said, I've found out the hard way and through about 400 hours of testing that most of us have been defragmenting our junk incorrectly and that it's better to not defrag at all rather than to defrag incorrectly. Doing things correctly involves a wee bit of work but I can tell you, stop using REORGANIZE. It's been mostly documented correctly as to how it works but everyone mistakes what it says and it causes big problems. And, it's not the friendly little thing that a lot of people think especially but not limited to large indexes. When they say "it's fully logged", them mean it and in spades!
You also need to stop rebuilding indexes with a 0% fill factor. Rebuilding them at 0% is the same as building them at 100% and if you don't know the insert/update/delete pattern of the index, then your index maintenance may (will probably) end up being a major source of blocking on the morning after your index maintenance just like it was for me. If you need to recover some disk space, rebuild indexes that have less than 80% page density at 82% Fill Factor until you know more about the indexes. Even that can be a space waster, though. There are tradeoffs and fixes that are way too long to include in a single post.
There's actually a bunch of rules I'm working on for how to defrag indexes to reduce page splits without wasting a shedload of memory but I've not completed my suggestions yet... especially since "ExpAnsive" updates can put such a twist on fragmentation.