The CCALL instruction's design allows not only untraced function
pointers as the callee, but also allow system calls and so on. The
separation of "callee type" and "callee signature" -- where the callee
type is usually just `ufunctpr<sig>` -- may cause some confusion.