John,
Looking at that DBCC output, the only tables I see it has high frag is JournalArchive and Saveset:
DBCC SHOWCONTIG scanning 'JournalArchive' table...
Table: 'JournalArchive' (37575172); index ID: 6, database ID: 14
LEAF level scan performed.
- Pages Scanned................................: 14653
- Extents Scanned..............................: 1840
- Extent Switches..............................: 5419
- Avg. Pages per Extent........................: 8.0
- Scan Density [Best Count:Actual Count].......: 33.80% [1832:5420]
- Logical Scan Fragmentation ..................: 27.63%
- Extent Scan Fragmentation ...................: 67.50%
- Avg. Bytes Free per Page.....................: 3792.8
- Avg. Page Density (full).....................: 53.14%
DBCC SHOWCONTIG scanning 'Saveset' table...
Table: 'Saveset' (117575457); index ID: 5, database ID: 14
LEAF level scan performed.
- Pages Scanned................................: 132822
- Extents Scanned..............................: 16646
- Extent Switches..............................: 27766
- Avg. Pages per Extent........................: 8.0
- Scan Density [Best Count:Actual Count].......: 59.79% [16603:27767]
- Logical Scan Fragmentation ..................: 12.64%
- Extent Scan Fragmentation ...................: 24.69%
- Avg. Bytes Free per Page.....................: 107.4
- Avg. Page Density (full).....................: 98.67%
DBCC SHOWCONTIG scanning 'Saveset' table...
Table: 'Saveset' (117575457); index ID: 13, database ID: 14
LEAF level scan performed.
- Pages Scanned................................: 135713
- Extents Scanned..............................: 17012
- Extent Switches..............................: 33975
- Avg. Pages per Extent........................: 8.0
- Scan Density [Best Count:Actual Count].......: 49.93% [16965:33976]
- Logical Scan Fragmentation ..................: 15.60%
- Extent Scan Fragmentation ...................: 33.87%
- Avg. Bytes Free per Page.....................: 1580.6
- Avg. Page Density (full).....................: 80.47%
You can reorganize/rebuild these indexes manually from SQL Management Studio. If you are not familiar with this process, take a look at this technote and use the SQL script to rebuild any index with fragmentation over 10% *(or reorganize any index under 10%):
SQL Index Fragmentation and Statistics
http://www.symantec.com/docs/TECH168905
If after running that script you still see high fragmentation, you might need to get Microsoft to deep a little bit more on this.
I hope this helps.