It would possibly make sense to force a check for modification outside the IDE, but not do a silent reload.
If I see it right,C::B only checks for modified files, if one of the "New"-submenus was called, the app gets (re-)activated or we swap between header and sourcefile.
Reloading a file without asking would irreversible delete all changes that have been made, because the undo-history would also be cleared.
Ctrl-z is enought to revert also very many changes, just keep the keys pressed and it will revert everything until the point the undo-buffer was cleared the last time.
That (the undu-buffer-clearing) happens in three cases: a file gets (re-)loaded, you switch changebar on, if it wasn't, or you clear the buffer explicitely via the (context-)menu.
And that also works if you have saved the file after opening it, as it always happens when the newly added code was compiled to test it.
So a menu-entry to force a check for modified files would make sense in my eyes (at least for files that get changed by the program, that the user works on, egally if that happens for debugging purposes or anything else), but a force-file-reload is not only unnecessary, but can be really dangerous, because it might lead to data-loss.