Or is this a "six of one, half-a-dozen of the other" sort of question, which really will boil down to personal preference?
From reading the MSDN description of the "Check DB Integrity" task, it sounds like it will do what DBCC CheckDB does, although possibly the "reporting" of problems might not be a "full featured" as from a custom script.
Any thoughts?
Beyond the obvious of "why aren't you already checking your DBs?"
(Answer: I inherited the current situation, and am working on resolving stuff like this)
Thanks,
Jason