In phpDocumentor 1, <code> tags could be used to generate a code block. This was definitely supported in long descriptions. I'm not sure if it was supported elsewhere.
I'm not sure whether this was supported in phpDocumentor 2, but it definitely isn't supported in 3.
Support being dropped, in itself, is not a problem as the markdown "_triple backtick, optionally with language_" syntax can be used instead.
However, I couldn't find anything about when support for this was dropped in the documentation and/or changelog, nor in an upgrade guide,
So that makes me wonder if dropping support was an oversight (unintentional), in which case, this is a bug report.
If the dropping of the support _was_ intentional, or if it would be decided based on this issue that it is retroactively no longer supported, I'd like to suggest adding a changelog entry to the phpDocumentor version in which this was dropped and to make sure it is included in an end-user upgrade guide.
I can also imagine that any instances of <code> found in the docs could be listed in the "Deprecated" or "Error" report to make it easier for end-user devs to update their docs to use the triple backtick.
That use of <code> would either still be supported or would generate a warning/error and that the dropping it would be mentioned somewhere.
Code sample:
/**
* Retrieve information.
*
* The return value is in the following format:
*
* <code>
* 0 => array(
* 'name' => '$var', // The variable name.
* 'token' => integer, // The stack pointer to the variable name.
* )
* </code>
*
* @return array
*/
function foo() {}
Both the <code> tags, as well as the text between them, is treated like ordinary text and no deprecations/errors/markers are shown in the reports.

php -f /path/to/phpDocumentor/bin/phpdocJust found issue #685. Based on that the <code> tag was supported in phpDocumentor 2.
I don't remember what happened to this. I am not opposed to reintroducing this. As this is a code change, I will have to defer working on this until I am done with the template changes