The first question is why you want to switch back to read-write? If you're planning on doing file/filegroup backups and relying on the fact that you won't need more than one restore for those read only files, than this switch to read-write and back to read-only will be messing that up quite nicely as the files are no longer assumed to be static from the time they were first made read-only
I have to ask, why does the MS advice sound 'odd' when what CheckDB does normally is take a database snapshot of the entire database and run against that?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability