Overhead associated with DBCC CHECKTABLE?

Have a logshipped VLDB and don't run **DBCC CHECKDB** on primary due to the long running periods of high CPU and tempdb usage. Have read about **DBCC CHECKTABLE** as a possibility for a more granular data integrity checking option. Does **DBCC CHECKTABLE** have overhead levels similar to **DBCC CHECKDB**? Can it be run during business hours without adversely affecting server CPU and TempDB performance?